-
Notifications
You must be signed in to change notification settings - Fork 6
Railpack doc #262
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Railpack doc #262
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
a few wording changes
docs/concepts/railpack.mdx
Outdated
|
||
## How to trigger a Defang Railpack deployment | ||
|
||
When you run a Defang Railpack deployment you need 2 components: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When you run a Defang Railpack deployment you need 2 components: | |
When you run a Defang Railpack deployment, you need 2 components: |
docs/concepts/railpack.mdx
Outdated
|
||
[Railpack](https://railpack.com/) is a tool for building container images from source code with minimal configuration. It is the successor to [Nixpacks](https://nixpacks.com/) and incorporates several lessons learned from running Nixpacks in production at [Railway](https://railway.com/) over the years. | ||
|
||
In Defang deployments, one of the most common points of failure is a missing or invalid Dockerfile that can’t produce OCI-compliant images. This is especially common when Dockerfile are generated by LLMs or created by users with limited Docker experience. Since integrating Railpack into Defang, if no Dockerfile is provided, we now automatically build a working image for you using Railpack. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In Defang deployments, one of the most common points of failure is a missing or invalid Dockerfile that can’t produce OCI-compliant images. This is especially common when Dockerfile are generated by LLMs or created by users with limited Docker experience. Since integrating Railpack into Defang, if no Dockerfile is provided, we now automatically build a working image for you using Railpack. | |
In Defang deployments, one of the most common issues faced by users is a missing or invalid Dockerfile that can’t produce OCI-compliant images. This is especially common when Dockerfiles are generated by LLMs or created by users with limited Docker experience. Since integrating Railpack into Defang, if no Dockerfile is provided, we now automatically build a working image for you using Railpack. |
docs/concepts/railpack.mdx
Outdated
|
||
### Railpack Detection | ||
|
||
To allow Railpack to generate a build plan for your project, please structure it to include the following files, or rename existing ones to be compatible. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To allow Railpack to generate a build plan for your project, please structure it to include the following files, or rename existing ones to be compatible. | |
To allow Railpack to generate a build plan for your project, please restructure or rename your existing project files to be Railpack-compatible, as described for each framework below. |
docs/concepts/railpack.mdx
Outdated
|
||
Your project will be detected as a Elixir application if any of these conditions are met: | ||
|
||
- A mix.exs file exists in the root directory. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- A mix.exs file exists in the root directory. | |
- A mix.exs file exists in the root directory |
Document for Railpack